+-------------------------------------+ ¦ =MooDoo= Script Manager Version 4.0 ¦ ¦ FAQ ¦ ¦ Revision 1 ¦ +-------------------------------------+ GET ORGANIZED. GET =MOODOO=. +-------------------------------------+ ¦=MooDoo Script Manager 4.0 FAQ Rev. 1¦ ¦Copyright © 1997 I Make Poole, Inc. ¦ +-------------------------------------+ Contents SECTION 1 - Architectural Questions 1. How do I load scripts automatically? 2. What is a default script and how do I use it? 3. What does logging log? 4. What does 'Inserting the correct path' mean? 5. What about 'Auto inserting correct path'? 6. How do I work with the Custom menu? 7. How do I work with the Script Database? 8. How does 'Management' help me? SECTION 2 - Problems 1. I load a script, and the aliases and/or popups, etc. are not loaded. 2. When I load a script that tries to access its files, it cannot. SECTION 3 - Fun Stuff 1. Script Manager 4.0 ALL-BUGS-FIXED 2. The Secret Messages 3. Distribution 4. What Hawkee Said About =MooDoo= 5. Where =MooDoo= Is Available (For Reference) SECTION 1 - Architectural Questions 1. How do I load scripts automatically? Use the fetch command provided. The fetch command will automatically load all the necessary script files for the script. All you need to specify is the script's mirc.ini. The fetch command is located under Fetch | Fetch Script. 2. What is a default script and how do I use it? A default script is set with Set | Default Script. Once it is set, it is automatically loaded when you press F2, type /default, or use the Fetch | Default Script command. This feature is useful for scripts you use very often. 3. What does logging log? Logging logs the status window where all the =MooDoo= messages are displayed. 4. What does 'Inserting the correct path' mean? When you use INI Files | Insert Correct Path on an mirc.ini, it replaces the specified paths of the aliases.ini, popups.ini, etc. with the path of the mirc.ini. This is helpful for ignorant people who set the paths as c:\myscript\inifiles\aliases.ini. 5. What about 'Auto inserting correct path'? The option INI Files | Auto Insert Path On Fetch does the same thing as Insert Correct Path, but it runs (if set to) automatically as soon as you fetch a script. 6. How do I work with the Custom menu? The Generate and Add commands on the Custom menu are used for scripts that have NO MIRC.INI. Such scripts cannot be fetched by the Script Manager. Therefore, you can create a default mirc.ini with Generate Default MIRC.INI, and then specify the aliases, popups, etc. in the generated ini file with Add To Generated INI. 7. How do I work with the Script Database? The script database is used to store script information for fast access. New Entry is used to add an entry, where you specify the name and the ini it points to. Erase entry is used to erase such an entry. Clear Database is pretty self-explanatory. Show Entries prints out a list of all you Database entries. Entry Info shows the ini the entry points to and the date it was created. 8. How does 'Management' help me? This is a somewhat limited feature for now. I am planning to expand on it, though. Install Script | Setup runs the setup program for a script. Install Script | ZIP unzips a selected zip file into a subdirectory. SECTION 2 - Problems 1. I load a script, and the aliases and/or popups, etc. are not loaded. This is most likely because the files specified in the mirc.ini are specified without a path, and have the same names as those in your Manager's directory. All you have to do is exit the mIRC, run INI | Insert Correct Paths on the mirc.ini and fetch it once more. If this happens to you alot, consider the Auto Insert Paths On Fetch option. 2. When I load a script that tries to access its files, it cannot. This is happening for one of two reasons. For one, it might be that the script tries to access the files incorrectly. But two, it might be that the script is trying to access files without a path. When this happens, mIRC looks in its own directory and doesn't find them. You can do several things. You can insert correct paths into the script. You can move the files to the mIRC directory (which really defeats the purpose of a script manager). I am working on fixing this problem in the next version. Have faith. SECTION 2 - Fun Stuff 1. Script Manager 4.0 ALL-BUGS-FIXED When I made 3.9, I said it would most likely be the final version except for a chance of a bugfix coming out. Well I made the bugfix and all, but then decided that I would indeed continue with Script Manager. So I never released this version. Now, people have asked me about it, and to clarify everything, the version 4.0 ALL-BUGS-FIXED was never released. Only 3 people in the world have it in their posession. (Wow.) 2. The Secret Messages I decided to put in some secret messages into this script, just in the spirit of mIRC Cookies. Now, are they hard to find? No. Are they hard to understand? Yes, if you don't know what you are looking at. My hint is that you can reach them by echoing a certain identifier and that they use an underscore in their name. 3. Distribution =MooDoo= Script Manager 4.0 is currently available in ZIP and self-extracting zipfile formats. http://www.geocities.com/SiliconValley/Heights/8917/moodoo.html 4. What Hawkee Said About =MooDoo= "A unique little script with an innovative idea of storing databases for multiple scripts. Very nice scripting and a tidy interface and is very good for it's purpose. I recommend this for persons who use multiple scripts on IRC." 5. Where =MooDoo= SM39 Is Available (For Reference) =MooDoo= Homepage (http://www.geocities.com/SiliconValley/Heights/8917/moodoo.html) The mIRC Archive at tera-byte (http://www.tera-byte.com/mirc/) Hawkee's Scripts Page (http://www.hawkee.com) Talk about secret messages, huh? =) GET ORGANIZED. GET =MOODOO=.